Fast data transfer communication protocol for an industrial process network

ABSTRACT

A method of transferring data between a host device and a field device on an industrial process network includes transmitting, by the host device to the field device, a fast data transfer initiate request to request a subsequent data transfer between the host device and the field device via a fast data transfer communication protocol. The method further includes receiving, by the host device from the field device, a fast data transfer confirmation indicating, and transmitting, by the host device to the field device, a generic data transfer initiate request to request the subsequent data transfer with the field device. The method further includes receiving, by the host device from the field device, a generic data transfer initiate confirmation, and executing, responsive to the generic data transfer initiate confirmation, the subsequent data transfer between the host device and the field device via the fast data transfer protocol.

BACKGROUND

The present disclosure relates generally to data transfer on anindustrial process network. More particularly, the present disclosurerelates to a fast data transfer communication protocol between deviceson the industrial process network.

In a typical industrial plant, a distributed control system (DCS) isused to control many of the industrial processes performed at the plant.Typically, the plant has a centralized control room having a computersystem with user input/output (I/O), disc I/O, and other peripherals.Coupled to the computer system are a controller and a process I/Osubsystem. The process I/O subsystem includes I/O ports, which areconnected to various field devices throughout the plant. Field devicesinclude various types of analytical equipment, such as pressure sensors,temperature sensors, switches, transducers, valve positioners andactuators, as well as any other device that performs a function in adistributed control system.

Traditionally, analog field devices have been connected to the controlroom by two-wire twisted pair current loops, with each device connectedto the control room by a single two-wire twisted pair. Analog fielddevices are capable of responding to or transmitting an electricalsignal within a specified range. In a typical configuration, it iscommon to have a voltage differential of approximately 20-25 voltsbetween the two wires of the pair and a current of 4-20 milliampsrunning through the loop. An analog field device that transmits a signalto the control room modulates the current running through the currentloop, with the current proportional to a sensed process variable. On theother hand, an analog field device that performs an action under controlof the control room is controlled by the magnitude of the currentthrough the loops, which is modulated by the I/O port of the process I/Osystem, which in turn is controlled by the controller.

Historically, most traditional field devices have had either a singleinput or a single output that was directly related to the primaryfunction performed by the field device. For example, often the onlyfunction implemented by a traditional analog resistive temperaturesensor is to transmit a temperature by modulating the current flowingthrough the two-wire twisted pair, while the only function implementedby a traditional analog valve positioner is to position a valve betweenan open and closed position based on the magnitude of the currentflowing through the two-wire twisted pair.

More recently, hybrid systems that superimpose digital data on thecurrent loop have been used in process control systems. One hybridsystem is known in the control art as the Highway Addressable RemoteTransducer (HART) and is similar to the Bell 202 modem specification.The HART system uses the magnitude of the current in the current loop tosense a process variable (as in the traditional system), but alsosuperimposes a digital carrier signal upon the current loop signal. Thecarrier signal is relatively slow, and can provide updates of asecondary process variable at a rate of approximately 2-3 updates persecond. Generally, the digital carrier signal is used to send secondaryand diagnostic information and is not used to realize the primarycontrol function of the field device. Examples of information providedover the carrier signal include secondary process variables, diagnosticinformation (including sensor diagnostics, device diagnostics, wiringdiagnostics, and process diagnostics), operating temperatures,temperature of the sensor, calibration information, deviceidentification information, materials of construction, configuration orprogramming information, or other types of information. Accordingly, asingle hybrid field device may have a variety of input and outputvariables and may implement a variety of functions.

Foundation Fieldbus is a multi-drop serial digital two-waycommunications protocol defined by the Instrument Society of America(ISA), and is intended for connecting field instruments and otherprocess devices (e.g., monitoring and simulation units) in distributedcontrol systems. Foundation Fieldbus allows enhanced digitalcommunication over previous process control loop methods whilemaintaining the ability to power process devices coupled to the Fieldbusloop and while meeting intrinsic safety requirements. For instance, theFoundation Fieldbus specification (i.e., including the physical layerspecification and the data link layer specification) defines networksthat transmit data at much higher data rates than traditional hybridsystems, such as at data rates up to 31.25 kilobits per second (Kbps)for an H1 Fieldbus network and data rates up to 2.5 megabits per second(Mbps) for an H2 Fieldbus network.

The Fieldbus Message Specification (FMS) defines a messaging protocolfor communications over the fieldbus, accomplished via VirtualCommunication Relationships (VCRs). The VCRs provide connection-basedchannels for the transfer of data between applications and/or devices.Devices on the fieldbus network communicate via both scheduled andunscheduled communications managed by a Link Master (LM) device that isdesignated as the Link Active Scheduler (LAS). During scheduledcommunications, the LAS device issues a compel data message to a fielddevice. In response, the field device publishes data over the network toone or more subscriber devices. Unscheduled communications areaccomplished via a token passing algorithm managed by the LAS device.The LAS device issues a pass token message in turn to each deviceincluded in a list of active devices on the network, often referred toas the live list. Upon receiving the pass token message, a field devicetransmits any unscheduled data until all of its data has been publishedor a configurable “maximum token hold time” has expired.

Due to the connection-based nature of the VCRs, data transmissions areaccomplished via a series of messages, each requiring a correspondingacknowledgment. Unacknowledged messages are retransmitted, therebyincreasing robustness of communications. However, such connection-basedtransactions introduce overhead to the communications scheme, which istime-limited by the maximum token hold time allotted to each device forunscheduled communications. Accordingly, transactions involving largeamounts of data, such as uploads and downloads of configuration dataand/or software images can be relatively slow, sometimes taking an houror more to complete the transaction. As such, the use ofconnection-based transactions can increase the time (and expense)associated with activities such as maintenance, debugging, and devicecommissioning, and thereby generally decreasing usability of the system.

SUMMARY

In one example, a method of transferring data between a host device anda field device on an industrial process network includes transmitting,by the host device to the field device, a fast data transfer initiaterequest to request a subsequent data transfer between the host deviceand the field device via a fast data transfer communication protocol.The method further includes receiving, by the host device from the fielddevice, a fast data transfer confirmation indicating that the fielddevice is configured for the subsequent data transfer via the fast datatransfer communication protocol, and transmitting, by the host device tothe field device, a generic data transfer initiate request to requestthe subsequent data transfer with the field device. The method furtherincludes receiving, by the host device from the field device, a genericdata transfer initiate confirmation indicating that the field device isconfigured for the subsequent data transfer, and executing, responsiveto the generic data transfer initiate confirmation, the subsequent datatransfer between the host device and the field device via the fast datatransfer protocol.

In another example, a method of transferring data between a host deviceand a field device on an industrial process network includes receiving,by the field device from the host device, a fast data transfer initiaterequest to request a subsequent data transfer between the host deviceand the field device via a fast data transfer communication protocol.The method further includes transmitting, by the field device to thehost device, a fast data transfer initiate confirmation indicating thatthe field device is configured for the subsequent data transfer via thefast data transfer communication protocol, and receiving, by the fielddevice from the host device, a generic data transfer initiate request torequest the subsequent data transfer with the field device. The methodfurther includes transmitting, by the field device to the host device, ageneric data transfer initiate confirmation indicating that the fielddevice is configured for the subsequent data transfer, and executing,responsive to the generic data transfer initiate confirmation, thesubsequent data transfer between the host device and the field devicevia the fast data transfer communication protocol.

In one example, a host device includes at least one processor, one ormore storage devices, and a transceiver configured to send and receivedata over an industrial process control network. The one or more storagedevices are encoded with instructions that, when executed by the atleast one processor, cause the host device to transmit, to a fielddevice via the transceiver, a fast data transfer initiate request torequest a subsequent data transfer between the host device and the fielddevice via a fast data transfer communication protocol. The one or morestorage devices are further encoded with instructions that, whenexecuted by the at least one processor, cause the host device toreceive, from the field device via the transceiver, a fast data transferconfirmation indicating that the field device is configured for thesubsequent data transfer via the fast data transfer communicationprotocol, and transmit, to the field device via the host transceiver, ageneric data transfer initiate request to request the subsequent datatransfer with the field device. The one or more storage devices arefurther encoded with instructions that, when executed by the at leastone processor, cause the hose device to receive, from the field devicevia the host transceiver, a generic data transfer initiate confirmationindicating that the field device is configured for the subsequent datatransfer, and execute, responsive to receiving the generic data transferinitiate confirmation from the field device, the subsequent datatransfer with the field device via the fast data transfer communicationprotocol.

In one example, a field device includes at least one processor, one ormore storage devices, and a transceiver configured to send and receivedata over an industrial process control network. The one or more storagedevices are encoded with instructions that, when executed by the atleast one processor, cause the field device to receive, from the hostdevice via the transceiver, a fast data transfer initiate request torequest a subsequent data transfer between the host device and the fielddevice via a fast data transfer communication protocol. The one or morestorage devices are further encoded with instructions that, whenexecuted by the at least one processor, cause the field device totransmit, to the host device via the transceiver, a fast data transferinitiate confirmation indicating that the field device is configured forthe subsequent data transfer via the fast data transfer communicationprotocol, and receive, from the host device via the transceiver, ageneric data transfer initiate request to request the subsequent datatransfer with the field device. The one or more storage devices arefurther encoded with instructions that, when executed by the at leastone processor, cause the field device to transmit, to the host devicevia the transceiver, a generic data transfer initiate confirmationindicating that the field device is configured for the subsequent datatransfer, and execute, responsive to transmitting the generic datatransfer initiate confirmation, the subsequent data transfer between thehost device and the field device via the fast data transfercommunication protocol.

In one example, an industrial process system includes a host device anda field device. The host device includes at least one processor, one ormore host storage devices, and a host transceiver configured to send andreceive data over an industrial process network. The one or more hoststorage devices are encoded with instructions that, when executed by theat least one host processor, cause the host device to transmit, to thefield device via the host transceiver, a fast data transfer initiaterequest to request a subsequent data transfer between the host deviceand the field device via a fast data transfer communication protocol.The one or more host storage devices are further encoded withinstructions that, when executed by the at least one host processor,cause the host device to receive, from the field device via the hosttransceiver, a fast data transfer confirmation indicating that the fielddevice is configured for the subsequent data transfer via the fast datatransfer communication protocol, and transmit, to the field device viathe host transceiver, a generic data transfer initiate request torequest the subsequent data transfer with the field device. The one ormore host storage devices are further encoded with instructions that,when executed by the at least one host processor, cause the host deviceto receive, from the field device via the host transceiver, a genericdata transfer initiate confirmation indicating that the field device isconfigured for the subsequent data transfer, and execute, responsive toreceiving the generic data transfer initiate confirmation from the fielddevice, the subsequent data transfer with the field device via the fastdata transfer communication protocol. The field device includes at leastone field device processor, one or more field device storage devices,and a field device transceiver configured to send and receive data overthe industrial process network. The one or more field device storagedevices are encoded with instructions that, when executed by the atleast one field device processor, cause the field device to receive,from the host device via the field device transceiver, the fast datatransfer initiate request. The one or more field device storage devicesare further encoded with instructions that, when executed by the atleast one field device processor, cause the field device to transmit, tothe host device via the field device transceiver, the fast data transferconfirmation, and receive, from the host device via the field devicetransceiver, the generic data transfer initiate request. The one or morefield device storage devices are further encoded with instructions that,when executed by the at least one field device processor, cause thefield device to transmit, to the host device via the field devicetransceiver, the generic download initiate confirmation, and execute,responsive to transmitting the generic download initiate confirmation,the subsequent data transfer with the host device via the fast datatransfer protocol.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a block diagram illustrating an industrial process networkincluding a host device and field devices that can implement a fast datatransfer communication protocol.

FIG. 2 is a block diagram of a field device.

FIG. 3 is a block diagram of a host device.

FIG. 4 is a sequence diagram illustrating a fast data download from ahost device to a field device.

FIG. 5 is a sequence diagram illustrating a fast data download from ahost device to multiple field devices.

FIG. 6 is a sequence diagram illustrating a fast data upload from afield device to a host device.

DETAILED DESCRIPTION

According to techniques of this disclosure, data transfers between ahost device and one or more field devices on a Foundation Fieldbusnetwork can be accomplished via a fast data transfer communicationprotocol. Rather than transfer data via a connection-based communicationsession, such as a virtual communication relationship (VCR), a systemimplementing techniques of this disclosure can broadcast data (e.g.,upload and/or download data) between the host device and field deviceusing a connectionless (e.g., broadcasting) communication protocol. Bybroadcasting the messages, rather than requiring acknowledgment ofreceipt via a connection-based session, the techniques can increase thespeed of data transmissions, as well as decrease the amount of datatraffic on the fieldbus network. Moreover, a broadcasted message can bereceived by multiple devices (e.g., multiple field devices), therebydecreasing the number of data transmissions necessary to communicate asame set of data to multiple devices. In some examples, a data receiver(e.g., a field device during data download, or a host device during dataupload) can utilize domain positioning information included in themessages to determine whether a transmitted message was not received. Insuch examples, the data receiver can request retransmission of themissed message, thereby enabling a more robust communication session.Accordingly, a system implementing techniques of this disclosure canincrease the speed and efficiency of data transmissions over aFoundation Fieldbus network.

FIG. 1 is a block diagram illustrating one embodiment of an industrialprocess network 10 that includes host device 12 and field devices14A-14N (collectively referred to herein as “field devices 14”) that canimplement a fast data transfer communication protocol. Although network10 will be described in the context of a process control/monitoringsystem using Foundation Fieldbus communication protocol withcommunication of messages over bus 16, techniques of this disclosure mayhave general applicability to digital networks having host and/or fielddevices that engage in message transactions.

Host device 12 may typically be located within a centralized controlroom in an industrial process plant. In other examples, host device 12can be a handheld device that can be attached and detached from bus 16at various locations. Bus 16 can be, for example, a two-wire twistedpair or a four-wire cable that provides a communication pathway overwhich messages can be sent. Bus 16 can support a plurality of devices ona single cable, although the number of devices on bus 16 may be based atleast in part on a target loop execution speed and/or intrinsic safetyrequirements. Accordingly, field devices 14 are illustrated anddescribed with respect to the example of FIG. 1 as including “N” fielddevices, where “N” represents an arbitrary number.

Host device 12 may typically act as a link active scheduler (LAS) ofnetwork 10. In its function as the LAS device, host device 12 maintainsa central schedule for all communications between devices on bus 16. Atleast one of the other devices in network 10 (e.g., one or more of fielddevices 14) can be configured to act as a link master (LM) device. An LMdevice can be configured to take over scheduling responsibilities of theLAS device should the LAS device fail or become inoperable. In someexamples, more than one LM device can be present on bus 16, therebyproviding further backup for scheduling responsibilities.

Field devices 14, in some examples, can be process instruments thatsense one or more process parameters and provide data based upon thesensed parameters. In certain examples, field devices 14 can be processactuators that provide a physical output based upon a command messagereceived, e.g., over bus 16. In some examples, one or more of fielddevices 14 can be process instruments and one or more of field devices14 can be process actuators. In certain examples, one or more of fielddevices 14 can include both sensing and actuating capabilities. Examplesof field devices 14 include, but are not limited to, silicon pressuresensors, capacitive pressure sensors, resistive temperature detectors,thermocouples, strain gauges, limit switches, on/off switches, flowtransmitters, pressure transmitters, capacitance level switches, weighscales, transducers, valve positioners, valve controllers, actuators,solenoids, and indicator lights.

As one example operation, host device 12 can act as a LAS device fornetwork 10, thereby maintaining a central schedule for communicationsbetween any one or more of host device 12 and field devices 14 over bus16. Host device 12 can initiate scheduled communications with fielddevices 14, such as by transmitting compel data messages to fielddevices 14, in turn, over bus 16 according to the central schedule. Inresponse to receiving a compel data message, the respective one of fielddevices 14 can transmit its scheduled communications data over bus 16.Scheduled communications data can include, for example, process variabledata sensed by the respective field device and used for control of theindustrial process. As another example, scheduled communications datacan include actuator state information (e.g., position information) ofthe respective one of field devices 14. In general, scheduledcommunications data can typically include data identified as critical toreal-time operation and control of the industrial process network, suchas data used by function blocks executing on field devices 14 to monitorand/or control operation of the industrial process.

As one example, host device 12 can transmit a compel data message tofield device 14A at a time identified by the central schedule forscheduled communications with field device 14A. In response to receivingthe compel data message, field device 14A can transmit its scheduledcommunications data over bus 16, such as process parameter data sensedby field device 14A (e.g., temperature data, pressure data, or othertypes of process parameter data). The transmitted data can be receivedby one or more of host device 12 and field devices 14B-14N (i.e., othersof field devices 14) that are configured to receive data transmissionsfrom field device 14A, often referred to as “subscriber” devices. Hostdevice 12 can transmit compel data messages to each of field devices 14that are included in a live list of devices (i.e., a list of fielddevices 14 configured to transmit data over bus 16) according to theschedule, thereby managing scheduled communications over bus 16 in adeterministic manner.

Host device 12 can further initiate unscheduled communications withfield devices 14 via a token passing algorithm. According to the tokenpassing algorithm, host device 12 can transmit a “pass token” message toeach of field devices 14, in turn, to initiate unscheduled datatransmissions from the respective field device. Unscheduled datatransmissions can include, for instance, configuration data, alarm data,event data, trend data, diagnostic data, status data, data for operatordisplays, or other types of data. In general, unscheduled data caninclude any data not identified as critical to real-time operation ofthe industrial process network, such as data that is not used byfunction blocks executing on field devices 14 to monitor and/or controloperation of the industrial process.

As an example, host device 12 can transmit a pass token message over bus16 to field device 14A. Field device 14A, in response to receiving thepass token message, can transmit any unscheduled data identified (e.g.,queued) by field device 14A for transmission over bus 16. Field device14A can transmit the unscheduled data until all of the unscheduled dataidentified for transmission has been transmitted over bus 16, or until aconfigurable “maximum token hold time” has elapsed. The maximum tokenhold time parameter can effectively define an unscheduled datatransmission time window within which field devices 14 can transmitunscheduled data. In some examples, each of field devices 14 can beconfigured with a same maximum token hold time, thereby defining a samelength of time for unscheduled data transmissions for each of fielddevices 14. In other examples, one or more of field devices 14 beconfigured with different maximum token hold times.

In examples where the maximum token hold time elapses prior to acomplete transmission of the unscheduled data, field device 14A canstore (e.g., queue) the unsent data for later transmission, such asduring the next unscheduled data transmission window. In examples wherefield device 14A transmits all of its unscheduled data prior toexpiration of the maximum token hold time, field device 14A can transmita token return message to host device 12 to indicate that it hascompleted its unscheduled data transmission. Host device 12 can transmita pass token message to each of field devices 14, respectively, whichcan each transmit unscheduled data over bus 16 as described with respectto field device 14A. In this way, host device 12 can manage unscheduleddata communications of field devices 14.

Scheduled and/or unscheduled communications over bus 16 can beaccomplished via VCRs between any one or more of host device 12 andfield devices 14. The VCRs provide connection-based channels for thetransfer of data between devices on bus 16. Any one or more of hostdevice 12 and field devices 14 can exchange data using the VCRs viamessages having a format defined by the Fieldbus Message Specification(FMS). FMS messages transmitted via the connection-based VCRs include amessage payload as well as overhead in the form of a message preamble, astart delimiter, a stop delimiter, and other meta data associated withthe message. FMS messages transmitted via the connection-based VCRs areacknowledged with a corresponding acknowledgement message from thereceiving device, thereby indicating that the message was received.Unacknowledged messages can be retransmitted, thereby increasingrobustness of system communications.

In some examples, unscheduled data transmissions can include an amountof data that exceeds a maximum defined size of a corresponding FMSmessage. In such examples, the data can be transmitted via a pluralityof FMS messages, each including an associated message preamble and othermessage overhead and requiring a corresponding acknowledgment from areceiving device. For instance, device configuration data and/orsoftware image data (i.e., a set of computer-readable instructionsexecutable by the device for operation of the device) can often spanmultiple FMS messages. In some cases, the amount of time to transmit thedata can exceed a maximum token hold time allotted to the device,thereby causing the data to be transmitted across multiple unscheduleddata transmission windows.

Accordingly, as described herein, one or more of host device 12 andfield devices 14 can exchange data over bus 16 via a fast data transfercommunication protocol. For instance, as is further described below,rather than transfer data via the connection-based VCR that includescorresponding acknowledgments for each transmitted message, one or moreof host device 12 and field devices 14 can broadcast data using aconnectionless communication protocol.

As one example operation, host device 12 can transmit, via a VCRestablished between host device 12 and field device 14A, a fast datatransfer initiate request to request a subsequent data transfer betweenhost device 12 and field device 14A via the fast data transfercommunication protocol. Field device 14A, responsive to receiving thefast data transfer initiate request, can transmit a fast data transferconfirmation to host device 12 via the VCR, the confirmation indicatingthat field device 14A is configured for the subsequent data transfer viathe fast data transfer communication protocol. Responsive to receivingthe confirmation, host device 12 can transmit, via the VCR, a genericdata transfer initiate request to request the subsequent data transferwith the field device. The generic data transfer initiate request can,in certain examples, be a data transfer initiate request defined by theFMS. One or more of the fast data transfer initiate request and thegeneric data transfer initiate request can include a broadcast networkaddress, such as a network address of an I/O port of host device 12configured to receive broadcast network communications. Field device 14Acan transmit a generic data transfer initiate confirmation via the VCRconfirming that field device 14A is configured for the subsequent datatransfer. Responsive to receiving the generic data transfer initiateconfirmation, host device 12 and field device 14A can execute thesubsequent data transfer via the fast data transfer protocol. Forinstance, executing the subsequent data transfer via the fast datatransfer protocol can include broadcasting the subsequent data transferto the identified broadcast network address (e.g., the address includedin one or more of the fast data transfer and generic data transferinitiate requests). In certain examples, broadcasting the subsequentdata transfer to the identified broadcast network address can includebroadcasting a plurality of messages to the broadcast network addresswithout receiving an acknowledgment including an indication of whetherany one of the plurality of messages was received.

As such, host device 12 and field devices 14 can implement a fast datatransfer communication protocol to transfer data via bus 16 withoutrequiring acknowledgment of individual messages. In this way, hostdevice 12 and field devices 14 can transfer large amounts of data, suchas configuration data and/or software image data, more quickly thancould otherwise be transferred via connection-based VCRs andcorresponding FMS messages. Accordingly, techniques of this disclosurecan decrease an amount of time (and associated expense) associated withsuch large-scale data transfers, such as during device commissioning,device maintenance, debugging, or other activities.

FIG. 2 is a block diagram of one embodiment of field device 14A ofFIG. 1. However, while illustrated and described with respect to fielddevice 14A, it should be understood that field devices 14 of FIG. 1 canbe substantially similar, such that field device 14A of FIG. 2 can beany of field devices 14.

As illustrated in FIG. 2, field device 14A can include communicationscontroller 18, medium attachment unit (MAU) 20, processor(s) 20, storagedevice(s) 24, sensor(s) 26, and signal processing circuitry 28. Sensor26 can sense one or more process parameters or variables and providecorresponding sensor signals to signal processing circuitry 28. Thesensor signals can include a primary variable (e.g., pressure) and asecondary variable (e.g., temperature). The secondary variable can beused by processor 22, in some examples, for correction or compensationof the sensor signal representing the primary variable.

Signal processing circuitry 28 typically includes analog-to-digitalconversion circuitry, as well as filtering and other signal processingto place the sensor signals into a format that can be used by processor22. For example, signal processing circuitry 28 can include any one ormore sigma delta analog-to-digital converters and digital filters toprovide digitized and filtered sensor signals to processor 22.

Processor 22, in one example, is configured to implement functionalityand/or process instructions for execution within field device 14A, suchas to coordinate the operation of field device 14A. For example,processor 22 can process instructions stored in storage device 24 toprocess data received over bus 16, receive and store sensor signalsgenerated by sensor 26 (e.g., within storage device 24), and create andselect data to be contained in messages that are transmitted from fielddevice 14A over bus 16. Examples of processor 22 can include any one ormore of a microprocessor, a controller, a digital signal processor(DSP), an application specific integrated circuit (ASIC), afield-programmable gate array (FPGA), or other equivalent discrete orintegrated logic circuitry.

Storage device 24 can be configured to store information within fielddevice 14 during operation. Storage device 24, in some examples, can bedescribed as a computer-readable storage medium. In some examples, acomputer-readable storage medium can include a non-transitory medium.The term “non-transitory” can indicate that the storage medium is notembodied in a carrier wave or a propagated signal. In certain examples,a non-transitory storage medium can store data that can, over time,change (e.g., in RAM or cache). In some examples, storage device 24 isnot long-term storage. Storage device 24, in some examples, is describedas a volatile memory, meaning that storage device 24 does not maintainstored contents when power to field device 14A is turned off. Examplesof volatile memories can include random access memories (RAM), dynamicrandom access memories (DRAM), static random access memories (SRAM), andother forms of volatile memories. In some examples, storage device 24 isused to store program instructions for execution by processor 22.Storage device 24, in one example, is used by software, firmware, orother application logic executing on processor 22 to temporarily storeinformation during program execution.

Storage device 24, in some examples, also includes one or morecomputer-readable storage media. Storage device 24 can be configured tostore larger amounts of information than volatile memory. Storage device24 can further be configured for long-term storage of information. Insome examples, storage device 24 includes non-volatile storage elements.Examples of such non-volatile storage elements can include magnetic harddiscs, optical discs, floppy discs, flash memories, or forms ofelectrically programmable memories (EPROM) or electrically erasable andprogrammable memories (EEPROM).

Communications controller 18 can serve as an interface between processor22 and MAU 20. For example, communications controller 18, which can bean ASIC, can receive data from MAU 20, decode the data, form the datainto bytes, and provide message data to be read by processor 22. Asanother example, communications controller 18 can receive bytes of datafrom processor 22, format the data into messages, and provide messagesto MAU 20 for transmission on bus 16. MAU 20 can provide networkconnection of field device 14A to bus 16. MAU 20 can be an integratedcircuit or discrete components.

FIG. 3 is a block diagram of one embodiment of host device 12 of FIG. 1.As illustrated, the overall architecture of host device 12 can besimilar to that of field devices 14, and includes communicationscontroller 30, MAU 32, processor(s) 34, storage device(s) 36, inputdevice(s) 38, and output device(s) 40. Each of communications controller30, MAU 32, processor 34, and storage device 36 can be substantiallysimilar to communications controller 18, MAU 20, processor 22, andstorage device 24 of field device 14A, respectively. For example,communications controller 30 can serve as an interface between processor34 and MAU 32 for sending and receiving message data over bus 16. Inaddition, storage device 36 can be described as a computer-readablestorage medium encoded with instructions which, when executed byprocessor 34, cause host device 12 to operate in accordance withtechniques described herein.

As illustrated in FIG. 3, host device 12 can further include inputdevice(s) 38 and output device(s) 40. Input device 38, in some examples,is configured to receive input from a user. Examples of input device 38can include any one or more of a mouse, a keyboard, a microphone, apresence-sensitive and/or touch-sensitive display, or other type ofdevice configured to receive input from a user. Output device 40 can beconfigured to provide output to a user. Examples of output device 40 caninclude a sound card, a video graphics card, a speaker, a light emittingdiode (LED), a display device such as a cathode ray tube (CRT) monitoror liquid crystal display (LCD), or other type of device for outputtinginformation in a form understandable to users or machines.

In some examples, storage device 40 can be encoded with instructionswhich, when executed by processor 34, cause processor 34 to execute auser interface (UI) application configured to allow user interactionwith one or more devices connected to network 10. For example, hostdevice 12 can execute a UI application that accepts input via inputdevice 38, such as input to identify one or more of field devices 14 anddata to be uploaded to or downloaded from the identified one or more offield devices 14. For instance, host device 12 can execute a UIapplication that accepts input to cause host device 12 to initiate adata upload and/or download with one or more of field devices 14 via afast data communications protocol, as is further described below.

FIG. 4 is a sequence diagram illustrating example operations of a fastdata download from host device 12 to field device 14A. While the exampleoperations are illustrated and described with respect to a fast datadownload from host device 12 to field device 14A, the example operationscan be applicable to fast data downloads from host device 12 to any oneor more of field devices 14.

Host device 12 can transmit a fast data transfer initiate request tofield device 14A to request a subsequent data transfer between hostdevice 12 and field device 14A via a fast data transfer communicationprotocol (42). For instance, host device 12 can transmit the fast datatransfer initiate request in response to receiving an input (e.g., userinput via a UI application) to download configuration data and/orsoftware image data to field device 14A. In some examples, host device12 can transmit the fast data initiate request via a connection-basedVCR established between host device 12 and field device 14A. In certainexamples, the fast data transfer initiate request can include anindication of a requested data rate of the subsequent data transfer.

Field device 14A, responsive to receiving the fast data transferinitiate request, can transmit a fast data transfer confirmation to hostdevice 12 indicating that field device 14A is configured for thesubsequent data transfer via the fast data transfer communicationprotocol (44). In some examples, field device 14A can transmit the fastdata transfer confirmation via the VCR established between host device12 and field device 14A. In certain examples, such as when the fast datatransfer initiate request received from host device 12 includes anindication of a requested data rate of the subsequent data transfer, thefast data transfer confirmation can include one or more of aconfirmation of the requested data rate or an indication of a secondrequested data rate, different than the requested data rate receivedfrom host device 12. In this way, field device 14A and host device 12can negotiate a data rate for the subsequent data transfer via the fastdownload initiate request and the fast download initiate confirmation.

Host device 12, responsive to receiving the fast data transferconfirmation, can transmit a generic data transfer initiate request tofield device 14A to request the subsequent data transfer with fielddevice 14A (46). In certain examples, host device 12 may not receive thefast data transfer confirmation from field device 14A. In such examples,host device 12 may retransmit the fast data transfer initiate request tofield device 14A a threshold number of times or until host device 12receives a fast data transfer confirmation message. The threshold numberof retransmits can range from zero (in which case host device 12 doesnot retransmit the request) to any non-zero number, such as one, two, ormore retransmits. If host device 12 does not receive the fast datatransfer confirmation message, host device 12 can execute the subsequentdata transfer via a plurality of FMS messages over the VCR, therebyhelping to ensure interoperability of field devices and/or host devicesoperable to execute the fast data transfer protocol within networks thatinclude field devices and/or host devices that are not operable toexecute the fast data transfer protocol.

The generic download initiate request can be a data transfer messagedefined by the FMS and transmitted via the VCR established between hostdevice 12 and field device 14A. The generic download initiate requestcan, in certain examples, include an indication of a category of data tobe downloaded via the subsequent data transfer (e.g., configurationdata, software image data, or other category of data). As in the exampleof FIG. 4, the fast download initiate request and the generic downloadinitiate request can be transmitted by host device 12 via separatemessages. In other examples, the fast download initiate request and thegeneric download initiate request can be transmitted via a singlemessage. For instance, the fast download initiate request can beappended to the generic download initiate request defined by the FMS.One or more of the fast download initiate request and the genericdownload initiate request can include a broadcast network address towhich a plurality of messages will be broadcast during the subsequentdata transfer.

Field device 14A can transmit, responsive to receiving the genericdownload initiate request, a generic download initiate confirmation tohost device 12 (48), such as via the VCR between host device 12 andfield device 14A. In addition, field device 14A can configure acommunications interface (e.g., a port of MAU 20) to receive thesubsequent data transfer at the broadcast network address associatedwith the subsequent data transfer.

In response to receiving the generic download initiate confirmation,host device 12 can initiate the subsequent data transfer with fielddevice 14A via the fast data transfer communication protocol (e.g., aconnectionless broadcasting protocol). For example, as illustrated inFIG. 4, host device 12 can execute the subsequent data transfer bybroadcasting the subsequent data transfer via a plurality of broadcastmessages (50A-50N, collectively referred to herein as “broadcastmessages 50”), such as to a broadcast network address included in one ormore of the fast data transfer initiate request or the generic datatransfer initiate request. Each of the plurality of broadcast messages50 can include a portion of data associated with the subsequent datatransfer. For instance, such as when the subsequent data transferincludes a software image to be loaded and/or executed by field device14A, each of broadcast messages 50 can include a portion of the softwareimage. Host device 12 can transmit broadcast messages 50 until thesubsequent data transfer is complete. Accordingly, broadcast messages 50are illustrated as including “N” broadcast messages, where “N” is anarbitrary number. In addition, in some examples, host device 12 canconfigure a maximum token hold time parameter of field device 14A toextend the time of unscheduled communications allotted to field device14A. For instance, host device 12 can transmit a message (e.g., amessage defined by the FMS to configure the token hold time) prior totransmitting broadcast messages 50. In this way, host device 12 can helpto decrease the total time over which the subsequent data transferoperates by helping to ensure that the entire subsequent data transferoccurs within a single unscheduled communications window.

Host device 12 can transmit broadcast messages 50 consecutively to fielddevice 14 without receiving acknowledgment from field device 14 that anyone or more of broadcast messages 50 were received by field device 14.In this way, host device 12 can help to decrease the amount of time overwhich the subsequent data transfer operates by reducing the messagingoverhead and time associated with acknowledgment messages. In certainexamples, each of broadcast messages 50 can include data positioninginformation that indicates a relative position of the data included inthe respective broadcast message within the data associated with thesubsequent data transfer. The data positioning information can include abeginning and/or ending memory address of data within the respectivebroadcast message. In certain examples, the data positioning informationcan include an indication of a sequential order of broadcast messages,such as an integer value representing the relative order of a particularbroadcast message within the plurality of broadcast messages 50. Assuch, each of broadcast messages 50 can include data positioninginformation indicating a relative position of the associated data withinthe subsequent data transfer. Accordingly, in certain examples, fielddevice 14A can compare the data positioning information received inbroadcast messages 50 to determine whether any one or more of broadcastmessages 50 was not received by field device 14A.

As one example, field device 14A can compare data positioninginformation included in broadcast message 50C with data positioninginformation included in broadcast message 50A to determine that dataassociated with broadcast message 50B was not received by field device14A. In such examples, field device 14A can transmit a retransmitrequest to host device 12 indicating a request that host device 12retransmit the portion of the data associated with the subsequent datatransfer that was included in broadcast message 50B. Host device 12 canretransmit the requested broadcast message (e.g., broadcast message 50B)in response to receiving the retransmit request.

Host device 12 can transmit a generic download terminate request tofield device 14A to indicate that the subsequent data transfer iscomplete (52). In some examples, the generic download terminate messagecan be transmitted via the VCR established between host device 12 andfield device 14A. Field device 14A can transmit (e.g., via the VCR) ageneric download terminate confirmation to host device 12 responsive toreceiving the generic download terminate request (54).

Accordingly, host device 12 and field device 14A (or any one or more offield devices 14) can execute a fast data transfer communicationprotocol to download data, such as configuration data and/or softwareimage data, from host device 12 to field device 14A. The described fastdata download can increase the speed and efficiency of data downloadsfrom host device 12 to field devices 14, thereby increasing usability ofnetwork 10 to monitor and/or control the industrial process.

FIG. 5 is a sequence diagram illustrating example operations of a fastdata download from host device 12 to field devices 14A and 14B. Asillustrated in FIG. 5, host device 12 can execute a fast data transfercommunication protocol to broadcast a subsequent data transfer to aplurality of field devices 14. While illustrated and described withrespect to a subsequent data transfer between host device 12 and two offield devices 14 (i.e., field device 14A and field device 14B), theexample operations can be applicable to subsequent data transfersbetween host device 12 and any number of field devices 14 (e.g., each offield devices 14).

As illustrated, the example operations of FIG. 5 to execute a fast datadownload from host device 12 to multiple field devices 14 can be similarin nature to the example operations of FIG. 4 to execute the fast datadownload from host device 12 to a single one of field devices 14. Ingeneral, the example operations of FIG. 5 extend the fast data downloadto multiple field devices 14 via separate initiation and terminationrequests to each of the multiple field devices.

As illustrated in FIG. 5, host device 12 can transmit a fast datatransfer initiate request to request a subsequent data transfer betweenhost device 12 and field device 14A via a fast data transfercommunication protocol (56). Responsive to receiving the fast datatransfer initiate request, field device 14A can transmit a fast datatransfer confirmation indicating that field device 14A is configured forthe subsequent data transfer via the fast data transfer communicationprotocol (58). Host device 12 can further transmit a fast data transferinitiate request to field device 14B to request the subsequent datatransfer between host device 12 and field device 14B (60). Responsive toreceiving the fast data transfer initiate request, field device 14B cantransmit a fast data transfer confirmation indicating that field device14B is configured for the subsequent data transfer via the fast datatransfer communication protocol (62).

Host device 12 can transmit a generic data transfer initiate request tofield device 14A (64), which can responsively transmit a generic datatransfer confirmation message to host device 12 (66). Host device 12 cantransmit a generic data transfer initiate request to field device 14B(68). Field device 14B can transmit a generic data transfer confirmationmessage to host device 12 to indicate that field device 14B isconfigured for the subsequent data transfer (70). One or more of fastdata transfer initiate request 56 and generic data transfer initiaterequest 64 to field device 14A can include a broadcast network addressto which a plurality of messages will be broadcast during the subsequentdata transfer. In addition, one or more of fast data transfer initiaterequest 60 and generic data transfer initiate request 68 to field device14B can include the same broadcast network address to which theplurality of messages will be broadcast. Accordingly, host device 12 canexecute the subsequent data transfer by broadcasting the subsequent datatransfer via a plurality of broadcast messages (72A-72N, collectivelyreferred to herein as “broadcast messages 72”). As illustrated,broadcast messages 72 can be received by both field device 14A and fielddevice 14B. In this way, rather than transmit separate messages to eachof field devices 14A and 14B, host device 12 can execute the subsequentdata transfer with both field device 14A and field device 14B via a sameset of broadcast messages 72, thereby decreasing the amount of networktraffic and execution time associated with the subsequent data transfer.

As further illustrated in FIG. 5, host device 12 can terminate thesubsequent data transfer by transmitting a generic download terminaterequest to field device 14A (74), receiving a corresponding genericdownload terminate confirmation from field device 14A (76), transmittinga generic download terminate request to field device 14B (78), andreceiving a corresponding generic download terminate confirmation fromfield device 14B (80).

FIG. 6 is a sequence diagram illustrating example operations of a fastdata upload from field device 14A to host device 12. As illustrated inFIG. 6, host device 12 can initiate an upload of data (e.g.,configuration data, status data, software image data, or other types ofdata) via a fast data transfer communication protocol. While describedwith respect to field device 14A, the example operations can beapplicable to any of field devices 14.

Host device 12 can transmit a fast upload initiate request to fielddevice 14A to request a subsequent data upload from field device 14A tohost device 12 via a fast data transfer communication protocol (82). Insome examples, the fast upload initiate request can be transmitted via aconnection-based VCR between host device 12 and field device 14A. Fielddevice 14A, responsive to receiving the fast upload initiate request,can transmit (e.g., via the VCR) a fast upload initiate confirmationindicating that field device 14A is configured for the subsequent dataupload via the fast data transfer communication protocol (84). Inresponse to receiving the fast upload initiate confirmation, host device12 can transmit an upload initiate request (86), which in certainexamples can be a FMS message sent via the VCR and configured toinitiate a data upload. In certain examples, the upload initiate requestcan be considered a generic upload initiate request. Field device 14Acan transmit an upload initiate confirmation (e.g., via the VCR)indicating that field device 14A is configured for the subsequent dataupload (88). In some examples, the upload initiate confirmation can beconsidered a generic upload initiate confirmation. One or more of thefast upload initiate request 82 and the upload initiate request 86 caninclude an indication of a broadcast network address at which hostdevice 12 is configured to receive the subsequent data upload. Fielddevice 14A can execute the subsequent data upload via a plurality ofbroadcast messages (90A-90N, collectively referred to herein as“broadcast messages 90”) transmitted to the broadcast network addressidentified in fast data upload initiate request 82 and/or uploadinitiate request 86.

Field device 14A can transmit broadcast messages 90 sequentially withoutreceiving an acknowledgment that host device 12 has received any one ormore of broadcast messages 90. In some examples, each of broadcastmessages 90 can include data positioning information indicating arelative position of data associated with a broadcast message within thedata associated with the subsequent data upload. Host device 12 cancompare the received data positioning information to determine whetherany one or more of broadcast messages 90 was not received by host device12. Host device 12 can send a retransmit request to field device 14A inresponse to determining that a broadcast message was not received, theretransmit request including an indication of the determined one ofbroadcast messages 90 that was not received by host device 12.

Each of broadcast messages 90 can include an indication of whether thebroadcast message is last in the sequence of broadcast messages 90. Forinstance, as illustrated, broadcast message 90N can include anindication (e.g., a bit or byte) that broadcast message 90N is last inthe sequence of broadcast messages, and others of broadcast messages 90can include an indication that they are not the last in sequence.

Responsive to receiving a last in sequence of broadcast messages 90,host device 12 can terminate the subsequent data upload by transmittingan upload terminate request to field device 14A (92), which can transmitan upload terminate confirmation in response (94).

While the invention has been described with reference to an exemplaryembodiment(s), it will be understood by those skilled in the art thatvarious changes may be made and equivalents may be substituted forelements thereof without departing from the scope of the invention. Inaddition, many modifications may be made to adapt a particular situationor material to the teachings of the invention without departing from theessential scope thereof. Therefore, it is intended that the inventionnot be limited to the particular embodiment(s) disclosed, but that theinvention will include all embodiments falling within the scope of theappended claims.

The invention claimed is:
 1. A method of transferring data between ahost device and a field device on an industrial process network, themethod comprising: transmitting, by the host device to the field device,a fast data transfer initiate request via a first initiate message torequest a subsequent data transfer between the host device and the fielddevice via a fast data transfer communication protocol, the fast datatransfer initiate request comprising a fast upload initiate request torequest that the field device broadcast the subsequent data from thefield device to a broadcast address via the fast data transfercommunication protocol; receiving, by the host device from the fielddevice, a fast data transfer confirmation via a first confirmationmessage indicating that the field device is configured for thesubsequent data transfer via the fast data transfer communicationprotocol; transmitting, by the host device to the field device, ageneric data transfer initiate request via a second initiate message torequest the subsequent data transfer with the field device; receiving,by the host device from the field device, a generic data transferinitiate confirmation via a second confirmation message indicating thatthe field device is configured for the subsequent data transfer; andexecuting, responsive to the generic data transfer initiateconfirmation, the subsequent data transfer between the host device andthe field device via the fast data transfer protocol; wherein one ormore of the fast data transfer initiate request and the generic datatransfer initiate request includes a broadcast network address; whereinexecuting the subsequent data transfer between the host device and thefield device comprises broadcasting, by the field device, the subsequentdata transfer to the broadcast network address and receiving, by thehost device, the subsequent data transfer via the fast downloadcommunication protocol via a plurality of broadcast messages, each ofthe plurality of broadcast messages including a portion of dataassociated with the subsequent data transfer; wherein each of theplurality of broadcast messages includes data positioning informationthat indicates a relative position, within the data associated with thesubsequent data transfer, of the portion of the data included in therespective broadcast message; wherein the plurality of broadcastmessages includes at least a first broadcast message and a secondbroadcast message, the second broadcast message received subsequent tothe first broadcast message; and wherein the method further comprises:comparing, by the host device, data positioning information included inthe first broadcast message to data positioning information included inthe second broadcast message; and determining, by the host device basedon the comparing, that a portion of the data associated with thesubsequent data transfer was not received by the host device; whereinexecuting the subsequent data transfer further comprises transmitting,by the host device to the field device, a retransmit request indicatinga request that the field device retransmit the portion of the data tothe broadcast network address via a third broadcast message, subsequentto the second broadcast message.
 2. The method of claim 1, whereintransmitting the fast data transfer initiate request, receiving the fastdata transfer initiate confirmation, transmitting the generic datatransfer initiate request, and receiving the generic data transferinitiate confirmation are performed via a connection-orientedcommunication session between the host device and the field device, andwherein executing the subsequent data transfer between the host deviceand the field device comprises broadcasting the subsequent data transfervia a connectionless communication protocol.
 3. The method of claim 1,wherein executing the subsequent data transfer between the host deviceand the field device comprises executing the subsequent data transfer ata data rate determined, at least in part, by the field device.
 4. Amethod of transferring data between a host device and a field device onan industrial process network, the method comprising: receiving, by thefield device from the host device, a fast data transfer initiate requestvia a first initiate message to request a subsequent data transferbetween the host device and the field device via a fast data transfercommunication protocol; transmitting, by the field device to the hostdevice, a fast data transfer initiate confirmation via a firstconfirmation message indicating that the field device is configured forthe subsequent data transfer via the fast data transfer communicationprotocol; receiving, by the field device from the host device, a genericdata transfer initiate request via a second initiate message to requestthe subsequent data transfer with the field device; transmitting, by thefield device to the host device, a generic data transfer initiateconfirmation via a second confirmation message indicating that the fielddevice is configured for the subsequent data transfer; and executing,responsive to the generic data transfer initiate confirmation, thesubsequent data transfer between the host device and the field devicevia the fast data transfer communication protocol; wherein one or moreof the fast data transfer initiate request and the generic data transferinitiate request includes a broadcast network address; wherein executingthe subsequent data transfer between the host device and the fielddevice comprises broadcasting the subsequent data transfer to thebroadcast network address via a plurality of broadcast messages usingthe fast data transfer communication protocol; wherein each of theplurality of broadcast messages includes: a portion of data associatedwith the subsequent data transfer; and data positioning information thatindicates a relative position, within the data associated with thesubsequent data transfer, of the portion of the data included in therespective broadcast message; wherein the plurality of broadcastmessages includes at least a first broadcast message and a secondbroadcast message, the second broadcast message received subsequent tothe first broadcast message; and wherein the method further comprises:comparing, by the field device, data positioning information included inthe first broadcast message to data positioning information included inthe second broadcast message; and determining, by the field device basedon the comparing, that a portion of the data associated with thesubsequent data transfer was not received by the field device; whereinexecuting the subsequent data transfer further comprises transmitting,by the field device to the host device, a retransmit request indicatinga request that the host device retransmit the portion of the data to thebroadcast network address via a third broadcast message, subsequent tothe second broadcast message.
 5. The method of claim 4, wherein the fastdata transfer initiate request comprises a fast download initiaterequest to request that the field device receive the subsequent datatransfer from the host device via the fast data transfer communicationprotocol, and wherein executing the subsequent data transfer comprisesreceiving, by the field device, the subsequent data transfer at thebroadcast network address via the plurality of broadcast messages. 6.The method of claim 4, further comprising: storing, by the field device,the data included in a respective broadcast message at a domain locationof non-volatile memory of the field device, the domain locationcorresponding to the data positioning information included within therespective broadcast message.
 7. The method of claim 4, wherein thefield device comprises a first field device, wherein the fast datatransfer initiate request comprises a first fast data transfer initiaterequest, wherein the fast data transfer initiate confirmation comprisesa first fast data transfer initiate confirmation, wherein the genericdata transfer initiate request comprises a first generic data transferinitiate request, and wherein the generic data transfer initiateconfirmation comprises a first generic data transfer initiateconfirmation, the method further comprising: receiving, by a secondfield device from the host device, a second fast data transfer initiaterequest to request the subsequent data transfer between the host deviceand the second field device via the fast download communicationprotocol; transmitting, by the second field device to the host device, asecond fast data transfer initiate confirmation indicating that thesecond field device is configured for the subsequent data transfer viathe fast download communication protocol; receiving, by the second fielddevice from the host device, a second generic data transfer initiaterequest to request the subsequent data transfer with the second fielddevice; transmitting, by the second field device to the host device, asecond generic data transfer initiate confirmation indicating that thesecond field device is configured for the subsequent data transfer; andexecuting the subsequent data transfer between the host device and thesecond field device via the fast download communication protocol.
 8. Themethod of claim 4, wherein receiving the fast data transfer initiaterequest, transmitting the fast data transfer initiate confirmation,receiving the generic data transfer initiate request, and transmittingthe generic data transfer initiate confirmation are performed via aconnection-oriented communication session between the host device andthe field device, and wherein executing the subsequent data transferbetween the host device and the field device comprises broadcasting thesubsequent data transfer via a connectionless communication protocol. 9.The method of claim 4, further comprising: negotiating, by the fielddevice with the host device, a data transfer rate of the subsequent datatransfer, wherein executing the subsequent data transfer between thehost device and the field device comprises executing the subsequent datatransfer at the negotiated data transfer rate.
 10. The method of claim4, further comprising: transmitting, by the field device to the hostdevice, a data transfer halt message requesting that the host devicehalt the subsequent data transfer; and transmitting, by the field devicesubsequent to transmitting the data transfer halt message, a datatransfer commence message to the host device requesting that the hostdevice commence the subsequent data transfer.
 11. A field devicecomprising: at least one processor; one or more storage devices; and atransceiver configured to send and receive data over an industrialprocess network, wherein the one or more storage devices are encodedwith instructions that, when executed by the at least one processor,cause the field device to: receive, from the host device via thetransceiver, a fast data transfer initiate request via a first initiatemessage to request a subsequent data transfer between the host deviceand the field device via a fast data transfer communication protocol;transmit, to the host device via the transceiver, a fast data transferinitiate confirmation via a first confirmation message indicating thatthe field device is configured for the subsequent data transfer via thefast data transfer communication protocol; receive, from the host devicevia the transceiver, a generic data transfer initiate request via asecond initiate message to request the subsequent data transfer with thefield device; transmit, to the host device via the transceiver, ageneric data transfer initiate confirmation via a second confirmationmessage indicating that the field device is configured for thesubsequent data transfer; and execute, responsive to transmitting thegeneric data transfer initiate confirmation, the subsequent datatransfer between the host device and the field device via the fast datatransfer communication protocol; wherein one or more of the fast datatransfer initiate request and the generic data transfer initiate requestincludes a broadcast network address; and wherein executing thesubsequent data transfer between the host device and the field devicecomprises broadcasting the subsequent data transfer to the broadcastnetwork address via the fast download communication protocol; whereineach of the plurality of broadcast messages includes: a portion of dataassociated with the subsequent data transfer; and data positioninginformation that indicates a relative position, within the dataassociated with the subsequent data transfer, of the portion of the dataincluded in the respective broadcast message; wherein the plurality ofbroadcast messages includes at least a first broadcast message and asecond broadcast message, the second broadcast message receivedsubsequent to the first broadcast message; and wherein the one or morestorage devices are further encoded with instructions that, whenexecuted by the at least one processor, cause the field device to:compare data positioning information included in the first broadcastmessage to data positioning information included in the second broadcastmessage; and determine, based on the comparing, that a portion of thedata associated with the subsequent data transfer was not received bythe field device; wherein executing the subsequent data transfer furthercomprises transmitting, by the field device to the host device, aretransmit request indicating a request that the host device retransmitthe portion of the data to the broadcast network address via a thirdbroadcast message, subsequent to the second broadcast message.
 12. Amethod of transferring data between a host device and a field device onan industrial process network, the method comprising: receiving, by thefield device from the host device, a fast data transfer initiate requestvia a first initiate message to request a subsequent data transferbetween the host device and the field device via a fast data transfercommunication protocol, the fast data transfer initiate requestcomprising a fast upload initiate request to request that the fielddevice broadcast the subsequent data transfer to the host device via thefast data transfer communication protocol; transmitting, by the fielddevice to the host device, a fast data transfer initiate confirmationvia a first confirmation message indicating that the field device isconfigured for the subsequent data transfer via the fast data transfercommunication protocol; receiving, by the field device from the hostdevice, a generic data transfer initiate request via a second initiatemessage to request the subsequent data transfer with the field device;transmitting, by the field device to the host device, a generic datatransfer initiate confirmation via a second confirmation messageindicating that the field device is configured for the subsequent datatransfer; and executing, responsive to the generic data transferinitiate confirmation, the subsequent data transfer between the hostdevice and the field device via the fast data transfer communicationprotocol; wherein one or more of the fast data transfer initiate requestand the generic data transfer initiate request includes a broadcastnetwork address; wherein executing the subsequent data transfer betweenthe host device and the field device comprises broadcasting, by thefield device, the subsequent data transfer to the broadcast networkaddress via a plurality of broadcast messages using the fast datatransfer communication protocol; wherein each of the plurality ofbroadcast messages includes: a portion of data associated with thesubsequent data transfer; and data positioning information thatindicates a relative position, within the data associated with thesubsequent data transfer, of the portion of the data included in therespective broadcast message; wherein the plurality of broadcastmessages includes at least a first broadcast message and a secondbroadcast message; wherein the second broadcast message is transmittedby the field device subsequent to transmitting the first broadcastmessage and without receiving an acknowledgment from the host devicethat includes an indication of whether the host device received thefirst broadcast message; and wherein executing the subsequent datatransfer further comprises: receiving, by the field device subsequent totransmitting the second broadcast message, a retransmit request from thehost device indicating a request that the field device retransmit theportion of the data associated with the subsequent data transfer thatwas included in the first broadcast message; and broadcasting, by thefield device to the broadcast network address, a third broadcast messagesubsequent to transmitting the second broadcast message, the thirdbroadcast message including the portion of the data associated with thesubsequent data transfer that was included in the first broadcastmessage.
 13. A field device comprising: at least one processor; one ormore storage devices; and a transceiver configured to send and receivedata over an industrial process network, wherein the one or more storagedevices are encoded with instructions that, when executed by the atleast one processor, cause the field device to: receive, from the hostdevice via the transceiver, a fast data transfer initiate request via afirst initiate message to request a subsequent data transfer between thehost device and the field device via a fast data transfer communicationprotocol, the fast data transfer initiate request comprising a fastupload initiate request to request that the field device broadcast thesubsequent data transfer to the host device via the fast data transfercommunication protocol; transmit, to the host device via thetransceiver, a fast data transfer initiate confirmation via a firstconfirmation message indicating that the field device is configured forthe subsequent data transfer via the fast data transfer communicationprotocol; receive, from the host device via the transceiver, a genericdata transfer initiate request via a second initiate message to requestthe subsequent data transfer with the field device; transmit, to thehost device via the transceiver, a generic data transfer initiateconfirmation via a second confirmation message indicating that the fielddevice is configured for the subsequent data transfer; and execute,responsive to transmitting the generic data transfer initiateconfirmation, the subsequent data transfer between the host device andthe field device via the fast data transfer communication protocol;wherein one or more of the fast data transfer initiate request and thegeneric data transfer initiate request includes a broadcast networkaddress; and wherein executing the subsequent data transfer between thehost device and the field device comprises broadcasting, by the fielddevice, the subsequent data transfer to the broadcast network addressvia a plurality of broadcast messages using the fast data transfercommunication protocol; wherein each of the plurality of broadcastmessages includes: a portion of data associated with the subsequent datatransfer; and data positioning information that indicates a relativeposition, within the data associated with the subsequent data transfer,of the portion of the data included in the respective broadcast message;wherein the plurality of broadcast messages includes at least a firstbroadcast message and a second broadcast message; wherein the secondbroadcast message is transmitted by the field device subsequent totransmitting the first broadcast message and without receiving anacknowledgment from the host device that includes an indication ofwhether the host device received the first broadcast message; andwherein the one or more storage devices are further encoded withinstructions that, when executed by the at least one processor, causethe field device to: receive, subsequent to transmitting the secondbroadcast message, a retransmit request from the host device indicatinga request that the field device retransmit the portion of the dataassociated with the subsequent data transfer that was included in thefirst broadcast message; and broadcast, to the broadcast networkaddress, a third broadcast message subsequent to transmitting the secondbroadcast message, the third broadcast message including the portion ofthe data associated with the subsequent data transfer that was includedin the first broadcast message.